-
-
Notifications
You must be signed in to change notification settings - Fork 11
887-refactor: Partners refactor #892
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Lighthouse Report:
|
Lighthouse Report:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see that the only test that is in the component does not check anything. Let's add unit tests that check the content output. Title, src and alt logos
Lighthouse Report:
|
src/widgets/partnered/partnered.tsx
Outdated
<WidgetTitle size="small">Partnered with</WidgetTitle> | ||
<div className="partners"> | ||
<div className="partner-logo-container"> | ||
<ul className={cx('partners')}> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we use the structure like in Alumni
widget?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understand a point of keeping a similar HTML structure in all our widgets
Difference for now:
Alumni
<article>
<section>
<WidgetTitle />
<Paragraph />
<section>
{alumni.map(() => (
<figure>
<Image />
</figure>
))}
</section>
</section>
</article>
Partnered
<section>
<div>
<WidgetTitle />
<ul>
{partners.map(() => (
<li>
<Component />
</li>
))}
</ul>
</div>
</section>
- All containers in widgets have
section
tag. - I't strange to have
article->section->section
structure - lists usually use
ul->li
tags
Therefore, I suggest to keep partnered html structure in both partnered
and alumni
widgets
Lighthouse Report:
|
π |
What type of PR is this? (select all that apply)
Description
Refactor partnered module
Related Tickets & Documents
Screenshots, Recordings
I changed a little bit styles for tablets and mobiles
Added/updated tests?
[optional] Are there any post deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?